Hello to all.
Original topic: hxxp://answers.microsoft.com/en-us/windows/forum/windows8_1-performance/sfc-verifyfile-doesnt-work-is-it-a-bug/17542cd5-1eee-4cb1-948c-d9ff68267e3a
I found that SFC /VERIFYFILE doesn't work on my machine.
I can't know if it doesn't work on each Windows 8/8.1 machine.
I saw this when I was trying to verify a well-known file prone to corruption (it is at least an year that this keeps to corrupt itself): CNBJ2530.DPB.
That file becomes corrupt for unknown reasons, from time to time.
Usually you can find Windows corrupt files through SFC /SCANNOW, wait for about half hour and check the CBS.LOG.
Given that the corrupt file is always THAT, I decided to try SFC /VERIFYFILE (few months ago), to save time.
To my surprise, it didn't work:
sfc /verifyfile=C:\Windows\winsxs\amd64_prncacla.inf_31bf3856ad364e35_6.3.9600.17415_none_95dd5540d57f8c01\Amd64\cnbj2530.dpb Windows Resource Protection could not perform the requested operation. (Italian: Protezione risorse di Windows: impossibile eseguire l'operazione richiesta.)
Yes, I used an elevated command prompt.
Yes, I've tried with double quotes... And single quotes, too.
The questions are: Doesn't it work just for me? Or Doesn't it work for everybody?
Thanks in advance for any replies and/or confirmations.
Operating System: Windows 8.1 x64 update 1.
- I changed the Windows font size from Control Panel\Appearance and Personalisation\Display, change the size of all items, larger (150%).
- I changed the setting NX=AlwaysOn (DEP always on), by:
bcdedit /set {current} nx AlwaysOn
- I modified the default rules of the firewall (I exported the standard criteria and saved in a file), created my own rules, blocked all outgoing connections (except those I created with my rules).
- Edited by xilolee Wednesday, February 25, 2015 5:41 PM